Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/profile/`[userId]/page.tsx:
- Around line 235-239: The code force-casts reputation to
ContributorReputationWithMetrics when rendering <ReputationDashboard>, which can
crash if the API returned ContributorReputation without metrics; instead, check
for reputation.metrics before casting and handle the missing-metrics case
gracefully—either render a fallback/placeholder UI or pass default metrics
(e.g., zeros) so ReputationDashboard always receives the expected shape; update
the prop handling in ReputationDashboard usage (or its prop type) to accept
ContributorReputation | ContributorReputationWithMetrics and guard/use default
values when metrics is undefined.

In `@components/profile/contribution-heatmap.tsx`:
- Line 12: Remove the unused import and parameter to fix lint warnings: delete
the unused named import isSameDay from the top import list and remove the unused
map callback parameter index (or rename it to _ if needed) in the component's
map/iteration where index is defined so both symbols are no longer unused;
ensure any logic relying on isSameDay is preserved or replaced with the used
utilities (format, subDays, startOfDay) and run the linter to confirm warnings
are resolved.
- Around line 151-169: The current month labels use the static MONTHS array and
can misalign with the actual 365-day heatmap; instead compute monthLabels from
the rendered weeks array: iterate over weeks (use each week’s first real day or
first non-null day), derive its month name/index, and only emit a label when the
month changes or at the first/last week; replace the static MONTHS usage in the
render block with the computed monthLabels so labels align with week columns
(refer to symbols weeks, monthLabels, and MONTHS in contribution-heatmap.tsx).

In `@components/profile/xp-display.tsx`:
- Around line 14-19: getLevelFromXp currently computes level/progress directly
from xp which allows negative xp to produce invalid results; clamp or normalize
xp to be non-negative at the top of getLevelFromXp (e.g., const safeXp =
Math.max(0, xp)) and then use safeXp for computing level, currentLevelXp,
nextLevelXp and progress so level, currentLevelXp and progress are always valid.

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/profile/`[userId]/page.tsx:
- Around line 27-40: The getMockMetrics function currently returns fabricated XP
and skill levels; replace those synthetic values with neutral fallbacks
(zeros/empty arrays) and change any UI that consumes
ContributorReputationWithMetrics["metrics"] to treat this fallback as “metrics
unavailable” (e.g., show a placeholder or a “metrics not available yet” state)
instead of rendering performance data; locate getMockMetrics and update its xp
to 0, skills to an empty array, and contributionHistory to zero/empty values,
and ensure the profile/[userId]/page.tsx render path checks for the neutral
fallback and displays the unavailable-state UI rather than synthetic metrics.

---

Nitpick comments:
In `@app/profile/`[userId]/page.tsx:
- Around line 266-279: Compute a single dashboardReputation before the JSX and
render <ReputationDashboard /> only once: create a const (e.g.,
dashboardReputation) that uses the existing reputation value and, if it lacks
metrics, spreads reputation and sets metrics: getMockMetrics(); then replace the
two conditional render branches inside <TabsContent> with a single
<ReputationDashboard reputation={dashboardReputation} />. Refer to the existing
symbols reputation, getMockMetrics(), ReputationDashboard and the
ContributorReputationWithMetrics shape when implementing this change.